Bandwidth part configurations for v2x communication

ABSTRACT

A user equipment (UE), comprising: higher layer circuitry configured to receive first information to configure a sidelink bandwidth part (BWP) and second information to configure one or more resource pool for sidelink transmission and/or reception; transmitting circuitry configured to transmit a physical sidelink control channel (PSCCH) and a physical sidelink shared channel (PSSCH), wherein the first information includes a configuration of numerologies for the PSCCH and PSSCH; and the second information includes a configuration of one or more resource pools for the PSCCH and PSSCH within the sidelink BWP.

TECHNICAL FIELD

The present disclosure relates generally to communication systems. Morespecifically, the present disclosure relates to bandwidth part (BWP)configurations for V2X communication.

BACKGROUND ART

Wireless communication devices have become smaller and more powerful inorder to meet consumer needs and to improve portability and convenience.Consumers have become dependent upon wireless communication devices andhave come to expect reliable service, expanded areas of coverage andincreased functionality. A wireless communication system may providecommunication for a number of wireless communication devices, each ofwhich may be serviced by a base station. A base station may be a devicethat communicates with wireless communication devices.

As wireless communication devices have advanced, improvements incommunication capacity, speed, flexibility and/or efficiency have beensought. However, improving communication capacity, speed, flexibility,and/or efficiency may present certain problems.

For example, wireless communication devices may communicate with one ormore devices using a communication structure. However, the communicationstructure used may only offer limited flexibility and/or efficiency. Asillustrated by this discussion, systems and methods that improvecommunication flexibility and/or efficiency may be beneficial.

SUMMARY OF INVENTION

In one example, a user equipment (UE), comprising: higher layercircuitry configured to receive first information to configure asidelink bandwidth part (BWP) and second information to configure one ormore resource pool for sidelink transmission and/or reception;transmitting circuitry configured to transmit a physical sidelinkcontrol channel (PSCCH) and a physical sidelink shared channel (PSSCH),wherein the first information includes a configuration of numerologiesfor the PSCCH and PSSCH; and the second information includes aconfiguration of one or more resource pools for the PSCCH and PSSCHwithin the sidelink BWP.

In one example, a base station (gNB), comprising: higher layer circuitryconfigured to transmit first information to configure a sidelinkbandwidth part (BWP) and second information to configure one or moreresource pool for sidelink communication; wherein the first informationincludes a configuration of numerologies for the PSCCH and PSSCH; andthe second information includes a configuration of one or more resourcepools for the PSCCH and PSSCH within the sidelink BWP.

In one example, a communication method by a user equipment (UE),comprising: receiving first information to configure a sidelinkbandwidth part (BWP) and second information to configure one or moreresource pool for sidelink transmission and/or reception; transmitting aphysical sidelink control channel (PSCCH) and a physical sidelink sharedchannel (PSSCH), wherein the first information includes a configurationof numerologies for the PSCCH and PSSCH; and the second informationincludes a configuration of one or more resource pools for the PSCCH andPSSCH within the sidelink BWP.

In one example, a communication method by a base station (gNB),comprising: transmitting first information to configure a sidelinkbandwidth part (BWP) and second information to configure one or moreresource pool for sidelink communication; wherein the first informationincludes a configuration of numerologies for the PSCCH and PSSCH; andthe second information includes a configuration of one or more resourcepools for the PSCCH and PSSCH within the sidelink BWP.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram illustrating one implementation of one or morebase stations (gNBs) and one or more user equipments (UEs) in whichbandwidth part (BWP) configurations for V2X communication may beimplemented.

FIG 2 is an example illustrating V2X services.

FIG. 3 illustrates an uplink-downlink timing relation.

FIG. 4 is a block diagram illustrating one implementation of a UE.

FIG. 5 is a diagram illustrating an example of a resource grid for thedownlink.

FIG. 6 is a diagram illustrating one example of a resource grid for theuplink.

FIG. 7 shows examples of several numerologies.

FIG. 8 shows examples of subframe structures for the numerologies thatare shown in FIG. 7.

FIG. 9 shows examples of slots and sub-slots.

FIG. 10 shows examples of scheduling timelines.

FIG. 11 shows examples of DL control channel monitoring regions.

FIG. 12 shows examples of DL control channel which includes more thanone control channel elements.

FIG. 13 shows examples of UL control channel structures.

FIG. 14 is a block diagram illustrating one implementation of a gNB.

FIG. 15 is a block diagram illustrating one implementation of a UE.

FIG. 16 illustrates various components that may be utilized in a UE.

FIG. 17 illustrates various components that may be utilized in a gNB.

FIG. 18 is a block diagram illustrating one implementation of a UE inwhich BWP configurations for V2X communication may be implemented.

FIG. 19 is a block diagram illustrating one implementation of a gNB inwhich BWP configurations for V2X communication may be implemented.

DESCRIPTION OF EMBODIMENTS

A user equipment (UE) is described. The UE includes higher layercircuitry configured to receive information on a resource pool forsidelink. The UE also includes transmitting circuitry configured totransmit a physical sidelink control channel (PSCCH) and a physicalsidelink shared channel (PSSCH). The information on the resource poolincludes information on a bandwidth part identity (BWP ID). Thetransmitting circuitry is configured to transmit the PSSCH on a BWPassociated with the BWP ID.

A base station (gNB) is also described. The gNB includes transmittingcircuitry configured to transmit information on a resource pool forsidelink. The gNB also includes receiving circuitry configured toreceive a PSCCH and a PSSCH. The information on the resource poolincludes information on a BWP ID. The receiving circuitry is alsoconfigured to receive the PSSCH on a BWP associated with the BWP ID.

A communication method by a UE is also described. The method includesreceiving information on a resource pool for sidelink. The method alsoincludes transmitting a PSCCH and a PSSCH. The information on theresource pool includes information on a BWP ID. The method furtherincludes transmitting the PSSCH on a BWP associated with the BWP ID.

A communication method by a gNB is also described. The method includestransmitting information on a resource pool for sidelink. The methodalso includes receiving a PSCCH and a PSSCH. The information on theresource pool includes information on a BWP ID. The method furtherincludes receiving the PSSCH on a BWP associated with the BWP ID.

The 3rd Generation Partnership Project, also referred to as “3GPP,” is acollaboration agreement that aims to define globally applicabletechnical specifications and technical reports for third and fourthgeneration wireless communication systems. The 3GPP may definespecifications for next generation mobile networks, systems and devices.

3GPP Long Term Evolution (LTE) is the name given to a project to improvethe Universal Mobile Telecommunications System (UMTS) mobile phone ordevice standard to cope with future requirements. In one aspect, UMTShas been modified to provide support and specification for the EvolvedUniversal Terrestrial Radio Access (E-UTRA) and Evolved UniversalTerrestrial Radio Access Network (E-UTRAN).

At least some aspects of the systems and methods disclosed herein may bedescribed in relation to the 3GPP LTE, LTE-Advanced (LTE-A) and otherstandards (e.g., 3GPP Releases 8, 9, 10, 11 and/or 12). However, thescope of the present disclosure should not be limited in this regard. Atleast some aspects of the systems and methods disclosed herein may beutilized in other types of wireless communication systems.

A wireless communication device may be an electronic device used tocommunicate voice and/or data to a base station, which in turn maycommunicate with a network of devices (e.g., public switched telephonenetwork (PSTN), the Internet, etc.). In describing systems and methodsherein, a wireless communication device may alternatively be referred toas a mobile station, a UE, an access terminal, a subscriber station, amobile terminal, a remote station, a user terminal, a terminal, asubscriber unit, a mobile device, etc. Examples of wirelesscommunication devices include cellular phones, smart phones, personaldigital assistants (PDAs), laptop computers, netbooks, e-readers,wireless modems, etc. In 3GPP specifications, a wireless communicationdevice is typically referred to as a UE. However, as the scope of thepresent disclosure should not be limited to the 3GPP standards, theterms “UE” and “wireless communication device” may be usedinterchangeably herein to mean the more general term “wirelesscommunication device.” A UE may also be more generally referred to as aterminal device.

In 3GPP specifications, a base station is typically referred to as aNode B, an evolved Node B (eNB), a home enhanced or evolved Node B(HeNB) or some other similar terminology. As the scope of the disclosureshould not be limited to 3GPP standards, the terms “base station,” “NodeB,” “eNB,” “gNB” and/or “HeNB” may be used interchangeably herein tomean the more general term “base station.” Furthermore, the term “basestation” may be used to denote an access point. An access point may bean electronic device that provides access to a network (e.g., Local AreaNetwork (LAN), the Internet, etc.) for wireless communication devices.The term “communication device” may be used to denote both a wirelesscommunication device and/or a base station. An eNB may also be moregenerally referred to as a base station device.

It should be noted that as used herein, a “cell” may be anycommunication channel that is specified by standardization or regulatorybodies to be used for International Mobile Telecommunications-Advanced(IMT-Advanced) and all of it or a subset of it may be adopted by 3GPP aslicensed bands (e.g., frequency bands) to be used for communicationbetween an eNB and a UE. It should also be noted that in E-UTRA andE-UTRAN overall description, as used herein, a “cell” may be defined as“combination of downlink and optionally uplink resources.” The linkingbetween the carrier frequency of the downlink resources and the carrierfrequency of the uplink resources may be indicated in the systeminformation transmitted on the downlink resources.

“Configured cells” are those cells of which the UE is aware and isallowed by an eNB to transmit or receive information. “Configuredcell(s)” may be serving cell(s). The UE may receive system informationand perform the required measurements on all configured cells.“Configured cell(s)” for a radio connection may include a primary celland/or no, one, or more secondary cell(s). “Activated cells” are thoseconfigured cells on which the UE is transmitting and receiving. That is,activated cells are those cells for which the UE monitors the physicaldownlink control channel (PDCCH) and in the case of a downlinktransmission, those cells for which the UE decodes a physical downlinkshared channel (PDSCH). “Deactivated cells” are those configured cellsthat the UE is not monitoring the transmission PDCCH. It should be notedthat a “cell” may be described in terms of differing dimensions. Forexample, a “cell” may have temporal, spatial (e.g., geographical) andfrequency characteristics.

Fifth generation (5G) cellular communications (also referred to as “NewRadio,” “New Radio Access Technology” or “NR” by 3GPP) envisions the useof time/frequency/space resources to allow for enhanced mobile broadband(eMBB) communication and ultra-reliable low-latency communication(URLLC) services, as well as massive machine type communication (MMTC)like services. A new radio (NR) base station may be referred to as agNB. A gNB may also be more generally referred to as a base stationdevice.

Various examples of the systems and methods disclosed herein are nowdescribed with reference to the Figures, where like reference numbersmay indicate functionally similar elements. The systems and methods asgenerally described and illustrated in the Figures herein could bearranged and designed in a wide variety of different implementations.Thus, the following more detailed description of severalimplementations, as represented in the Figures, is not intended to limitscope, as claimed, but is merely representative of the systems andmethods.

FIG. 1 is a block diagram illustrating one implementation of one or morebase stations (gNBs) 160 and one or more user equipments (UEs) 102 inwhich bandwidth part (BWP) configurations for V2X communication may beimplemented. The one or more UEs 102 communicate with one or more gNBs160 using one or more antennas 122 a-n. For example, a UE 102 transmitselectromagnetic signals to the gNB 160 and receives electromagneticsignals from the gNB 160 using the one or more antennas 122 a-n. The gNB160 communicates with the UE 102 using one or more antennas 180 a-n.

The UE 102 and the gNB 160 may use one or more channels 119, 121 tocommunicate with each other. For example, a UE 102 may transmitinformation or data to the gNB 160 using one or more uplink channels121. Examples of uplink channels 121 include a PUCCH (Physical UplinkControl Channel) and a PUSCH (Physical Uplink Shared Channel), PRACH(Physical Random Access Channel), etc. For example, uplink channels 121(e.g., PUSCH) may be used for transmitting UL data (i.e., TransportBlock(s), MAC PDU, and/or UL-SCH (Uplink-Shared Channel)).

Here, UL data may include URLLC data. The URLLC data may be UL-SCH data.Here, URLLC-PUSCH (i.e., a different Physical Uplink Shared Channel fromPUSCH) may be defined for transmitting the URLLC data. For the sake ofsimple description, the term “PUSCH” may mean any of (1) only PUSCH(e.g., regular PUSCH, non-URLLC-PUSCH, etc.), (2) PUSCH or URLLC-PUSCH,(3) PUSCH and URLLC-PUSCH, or (4) only URLLC-PUSCH (e.g., not regularPUSCH).

Also, for example, uplink channels 121 may be used for transmittingHybrid Automatic Repeat Request-ACK (HARQ-ACK), Channel StateInformation (CSI), and/or Scheduling Request (SR). The HARQ-ACK mayinclude information indicating a positive acknowledgment (ACK) or anegative acknowledgment (NACK) for DL data (i.e., Transport Block(s),Medium Access Control Protocol Data Unit (MAC PDU), and/or DL-SCH(Downlink-Shared Channel)).

The CSI may include information indicating a channel quality ofdownlink. The SR may be used for requesting UL-SCH (Uplink-SharedChannel) resources for new transmission and/or retransmission. Namely,the SR may be used for requesting UL resources for transmitting UL data.

The one or more gNBs 160 may also transmit information or data to theone or more UEs 102 using one or more downlink channels 119, forinstance. Examples of downlink channels 119 include a PDCCH, a PDSCH,etc. Other kinds of channels may be used. The PDCCH may be used fortransmitting Downlink Control Information (DCI).

Each of the one or more UEs 102 may include one or more transceivers118, one or more demodulators 114, one or more decoders 108, one or moreencoders 150, one or more modulators 154, a data buffer 104 and a UEoperations module 124. For example, one or more reception and/ortransmission paths may be implemented in the UE 102. For convenience,only a single transceiver 118, decoder 108, demodulator 114, encoder 150and modulator 154 are illustrated in the UE 102, though multipleparallel elements (e.g., transceivers 118, decoders 108, demodulators114, encoders 150 and modulators 154) may be implemented.

The transceiver 118 may include one or more receivers 120 and one ormore transmitters 158. The one or more receivers 120 may receive signalsfrom the gNB 160 using one or more antennas 122 a-n. For example, thereceiver 120 may receive and downconvert signals to produce one or morereceived signals 116. The one or more received signals 116 may beprovided to a demodulator 114. The one or more transmitters 158 maytransmit signals to the gNB 160 using one or more antennas 122 a-n. Forexample, the one or more transmitters 158 may upconvert and transmit oneor more modulated signals 156.

The demodulator 114 may demodulate the one or more received signals 116to produce one or more demodulated signals 112. The one or moredemodulated signals 112 may be provided to the decoder 108. The UE 102may use the decoder 108 to decode signals. The decoder 108 may producedecoded signals 110, which may include a UE-decoded signal 106 (alsoreferred to as a first UE-decoded signal 106). For example, the firstUE-decoded signal 106 may comprise received payload data, which may bestored in a data buffer 104. Another signal included in the decodedsignals 110 (also referred to as a second UE-decoded signal 110) maycomprise overhead data and/or control data. For example, the secondUE-decoded signal 110 may provide data that may be used by the UEoperations module 124 to perform one or more operations.

In general, the UE operations module 124 may enable the UE 102 tocommunicate with the one or more gNBs 160. The UE operations module 124may include a UE scheduling module 126.

The UE scheduling module 126 may perform BWP configurations for V2Xcommunication. 3GPP V2X services will be used to transport SAE J2735Basic Safety Message(s) (BSM). The BSM has two parts: part 1 containsthe core data elements (e.g., vehicle size, position, speed, headingacceleration, brake system status), and is transmitted approximately 10times per second. Part 2 contains a variable set of data elements drawnfrom many optional data elements, and is transmitted less frequentlythan part 1. The BSM is expected to have a transmission range of ˜1,000meters, and is tailored for localized broadcast required by V2V safetyapplications.

In Rel-14 LTE V2X (also known as LTE V2X), a basic set of requirementsfor V2X service in TR 22.885 is supported, which are consideredsufficient for basic road safety service. An LTE V2X enabled vehicle(e.g., a vehicle configured with a UE 102 that supports V2Xapplications) can directly exchange status information via the PC5interface. It should be noted that sidelink defines the procedures forrealizing a single-hop UE-UE communication, similar to Uplink andDownlink, which define the procedures for UE-base station (BS) and BS-UEaccess, respectively. Along the same lines, PC5 was introduced as thenew direct UE interface, similar to the Uu (UE-BS/BS-UE) interface.Thus, the PC5 interface is also known as sidelink at the physical layersuch as position, speed and heading, with other nearby vehicles,infrastructure nodes and/or pedestrians that are also enabled with LTEV2X.

Rel-16 NR provides higher throughput, lower latency and higherreliability as compared to LTE, via a combination of enchantments toprotocol numerology, usage of higher frequency bands (e.g., mm WaveFrequencies) and a selection of wider sub carrier spacings (SCS) (e.g.,30 kHz, 60 kHz, 120 kHz, and/or 240 kHz, in addition to the 15 kHz usedby LTE) to match the higher frequency bands, and process for beammanagement (BM). Rel-16 NR is expected to provide an enhanced V2Xservice (also referred to as NR V2X) that leverages the higherthroughput, lower latency and higher reliability provided by Rel-16 NRdata transport services.

Therefore, it is desirable to enable a process in the NR V2X UE 102 thatconfigures the physical layer to transmit different transmission beams,with different SCS, according to the available V2X frequency bands.

In NR, there are roughly two large frequency ranges specified in 3GPP.One is below 6 GHz (also referred to as sub 6 GHz or FR1). The other isabove 6 GHz (also referred to as millimeter wave or FR2. Depending onthe frequency ranges, the maximum bandwidth and subcarrier spacingvaries. In FR1, the maximum bandwidth is 100 MHz and in the FR2 rangethe maximum bandwidth is 400 MHz. Some subcarrier spacing (e.g., 15 kHzand 30 kHz) can be used only in FR1 and some subcarrier spacing (e.g.,120 kHz and 240 kHz) can be used in FR2 only, and some subcarrierspacing (e.g., 60 kHz) can be used both in the FR1 and FR2 range.

As mentioned above, two types of frequency ranges are defined in 3GPP.Sub 6 GHz range is called FR1, and millimeter wave range is called FR2.The exact frequency range for FR1 (sub 6 GHz) and FR2 (millimeter wave)may be defined as in Table 1. Table 2 provides examples of NR operatingbands in FR1. Table 3 provides examples of NR operating bands in FR2.Table 4 provides applicable synchronization signal (SS) raster entriesper operating band (FR1). Table 5 provides applicable SS raster entriesper operating band (FR2).

TABLE 1 Frequency Range Designation Corresponding Frequency Range FR1 450 MHz-6000 MHz FR2 24,250 MHz-52,600 MHz

TABLE 2 Uplink (UL) operating band Downlink (DL) operating band BSreceive BS transmit NR UE transmit UE receive Operating Total totalDuplex Band F_(UL) _(—) _(low)-F_(UL) _(—) _(high) BW F_(UL) _(—)_(low)-F_(UL) _(—) _(high) BW Mode n1 1920 MHz-1980 MHz 60 2110 MHz-2170MHz 60 FDD n2 1850 MHz-1910 MHz 60 1930 MHz-1990 MHz 60 FDD n3  1710Mhz-1785 MHz 75 1805 MHz-1880 MHz 75 FDD n5     824-849 MHz 25 869MHz-894 MHz 25 FDD n7 2500 MHz-2570 MHz 70 2620 MHz-2690 MHz 70 FDD n8880 MHz-915 MHz 35 925 MHz-960 MHz 35 FDD n20 832 MHz-862 MHz 30 791MHz-821 MHz 30 FDD n28 703 MHz-748 MHz 45 758 MHz-803 MHz 45 FDD n382570 MHz-2620 MHz 50 2570 MHz-2620 MHz 50 TDD n41 2496 MHz-2690 MHz 1942496 MHz-2690 MHz 194 TDD n50 1432 MHz-1517 MHz 85 1432 MHz-1517 MHz 85TDD n51 1427 MHz-1432 MHz 5 1427 MHz-1432 MHz 5 TDD n66 1710 MHz-1780MHz 70 2110 MHz-2200 MHz 90 FDD n70 1695 MHz-1710 MHz 15 1995 MHz-2020MHz 25 FDD n71 663 MHz-698 MHz 35 617 MHz-652 MHz 35 FDD n74 1427MHz-1470 MHz 43 1475 MHz-1518 MHz 43 FDD n75 N/A  1432 Mhz-1517 MHz 85SDL n76 N/A  1427 Mhz-1432 MHz 5 SDL n78 3300 MHz-3800 MHz 500 3300MHz-3800 MHz 500 TDD n77 3300 MHz-4200 MHz 900 3300 MHz-4200 MHz 900 TDDn79 4400 MHz-5000 MHz 600 4400 MHz-5000 MHz 600 TDD n80 1710 MHz-1785MHz 75 N/A SUL n81 880 MHz-915 MHz 35 N/A SUL n82 832 MHz-862 MHz 30 N/ASUL n83 703 MHz-748 MHz 45 N/A SUL n84 1920 MHz-1980 MHz 60 N/A SUL

TABLE 3 Uplink (UL) operating band Downlink (DL) operating band BSreceive BS transmit NR UE transmit UE receive Operating total totalDuplex Band F_(UL) _(—) _(low)-F_(UL) _(—) _(high) BW F_(UL) _(—)_(low)-F_(UL) _(—) _(high) BW Mode n257 26500 MHz-29500 MHz 3000 26500MHz-29500 MHz 3000 TDD n258 24250 MHz-27500 MHz 3260 24250 MHz-27500 MHz3260 TDD n260 37000 MHz-40000 MHz 3000 37000 MHz-40000 MHz 3000 TDD

TABLE 4 NR Operating SS Block SS Block Range of GSCN Band SCS pattern(First-<Step size>-Last) n1 15 kHz Case A [7039-<1>-7224] n2 15 kHz CaseA [6439-<1>-6624] n3 15 kHz Case A [6022-<1>-6258] n5 15 kHz Case A[2902-<1>-2973] 30 kHz Case B [2911-<1>-2964] n7 15 kHz Case A[8740-<1>-8958] n8 15 kHz Case A [3091-<1>-3192] n20 15 kHz Case A[2644-<1>-2727] n28 15 kHz Case A [2533-<1>-2667] n38 15 kHz Case A[8572-<1>-8958] n41 15 kHz Case A [9069]-<TBD>-[9199] 30 kHz Case C[9070-<1>-9198] n50 15 kHz Case A [4780-<1>-5049] n51 15 kHz Case A[4762-<1>-4764] n66 15 kHz Case A  [7039-<1>-[7326] 30 kHz Case B [7048-<1>-[7317] n70 15 kHz Case A  [6655-<1>-[6726] n71 15 kHz Case A[2062-<1>-2166] n74 15 kHz Case A [4924-<1>-5052] n75 15 kHz Case A[4780-<1>-5049] n76 15 kHz Case A [4762-<1>-4764] n77 30 kHz Case C [9628-<1>-10247] n78 30 kHz Case C [9628-<1>-9969] n79 30 kHz Case C[10393]-<TBD>-[10802]

TABLE 5 NR Operating SS Block SS Block Range of GSCN Band SCS pattern(First-<Step size>-Last) n257 120 kHz Case D [24306-<1>-24476] 240 kHzCase E [24308-<2>-24474] n258 120 kHz Case D [24175-<1>-24361] 240 kHzCase E [24176-<2>-24360] n260 120 kHz Case D [24913-<1>-25084] 240 kHzCase E [24916-<2>-25080]The systems and methods described herein cover aspects for referenceconfigurations (RS) for V2X communication in FR1 and FR2. Enhancementsto NR V2X (e.g., 3GPP Rel-16 V2X, V2X service) for reference signalconfigurations of a physical sidelink control channel (PSCCH) and/or aphysical sidelink shared channel (PSSCH) are described herein.

A demodulation reference signal may be configured by system informationblock(s) (SIB(s)) or by dedicated radio resource control (RRC)message(s). In addition, a UE 102 may be configured with one or multipleresource pools. A demodulation reference signal configuration may beassociated with each resource pool. Furthermore, NR supports two typesof waveform: one waveform is CP-OFDM and the other waveform isDFT-S-OFDM. Each resource pool may be associated with a type ofwaveform. An example of V2X services is illustrated in FIG. 2.

For a radio link between a base station (gNB) 160 and a first or secondUE 102, the following physical channels may be used (downlink is atransmission direction from gNB 160 to UE 102, and uplink is atransmission direction from UE 102 to gNB 160): physical broadcastchannel (PBCH); physical downlink control channel (PDCCH); physicaldownlink shared channel (PDSCH); physical uplink control channel(PUCCH); and/or physical uplink shared channel (PUSCH).

A PBCH may be used for broadcasting essential system information. A PBCHmay include master information block (MIB) and some other information. APDCCH may be used for transmitting control information in the downlinkand the PDCCH may include downlink control information (DCI). A PDSCHmay be used for transmitting remaining minimum system information(RMSI), other system information (OSI), paging, and downlink data(DL-SCH (downlink shared channel)). A PUCCH may be used for transmittinguplink control information (UCI). A PUSCH may be used for transmittinguplink data (UL-SCH (uplink shared channel) and the PUSCH may be usedfor transmitting UCI.

For the radio link between a base station (gNB) 160 and a first orsecond UE 102, the following physical signals may be used: primarysynchronization signal (PSS); secondary synchronization signal (SSS);tracking reference signal (TRS); channel state information referencesignal (CSI-RS); demodulation reference signal (DMRS); phase trackingreference signal (PTRS); and/or sounding reference signal (SRS).

A PSS and a SSS may be used for time/frequency synchronization anddetermination/detection of a physical cell identity (PCID). The PSS, theSSS, and the PBCH may be multiplexed as a SS/PBCH block, and one or moreSS/PBCH blocks may be transmitted in a serving cell. A TRS may be usedfor channel tracking at a UE side and transmitted in the downlink, andthe TRS may be one configuration of a CSI-RS resource. A CSI-RS may beused for measuring channel state information (CSI) and transmitted inthe downlink and a CSI-RS includes non-zero power CSI-RS for channelmeasurement or interference measurement, zero-power CSI-RS (ZP CSI-RS)for interference measurement. A DMRS may be used for demodulation ofphysical channels, and the DMRS may be defined for each channel. A PTRSmay be used for phase tracking to compensate phase noise and transmittedwith DMRS and PDSCH/PUSCH. The PTRS may be configured in FR2. A SRS maybe used for channel sounding in the uplink.

DCI may include scheduling information of a PDSCH or a PUSCH, the timingof HARQ-ACK (hybrid automatic repeat request-acknowledgement) bit(s),and modulation and coding schemes (MCS), DMRS port information, and soon. UCI may include HARQ-ACK bits and CSI. CSI may include one or moreof CQI (channel quality indicator), PMI (precoding matrix indicator), RI(rank indicator), LI (layer indicator), and CRI (CSI-RS index).

For support of V2X communication, the following physical channels may bedefined: physical sidelink broadcast channel (PSBCH); physical sidelinkcontrol channel (PSCCH); and/or physical sidelink shared channel(PSSCH).

PSBCH may be used for transmitting information on sidelink frame number,and so on. PSCCH may be used for indicating sidelink control information(SCI), and SCI may indicate resource allocation (scheduling) informationof resource(s) for a PSSCH, modulation and coding schemes, redundancyversion(s). A transmitter of a first UE 102 (e.g., UE 1) may transmitPSCCH to a receiver UE 102 (e.g., UE 2).

For support of V2X communication, the following physical signals may bedefined: primary sidelink synchronization signal (PSSS); secondarysidelink synchronization signal (SSSS); tracking reference signal (TRS);channel state information reference signal (CSI-RS); demodulationreference signal (DMRS); phase tracking reference signal (PTRS); and/orsounding reference signal (SRS). A PSSS and a SSSS may be used fortime/frequency synchronization and determination/detection of asynchronization source identity (ID), and the PSSS, the SSSS, and thePSBCH may be multiplexed as a SSS/PSBCH block.

-   -   Numerologies, frame and slot structures, resource blocks (RBs),        bandwidth parts (BWPs) are also described herein. In this        disclosure, unless otherwise noted, the size of various fields        in the time domain is expressed in time units        T_(c)=1/(Δf_(max)·N_(f)) where Δf_(max)=480·10³ Hz and        N_(f)=4096. The constant κ=T_(s)/T_(c)=64 where        T_(s)=1/(Δf_(ref) ·N_(f,ref)), Δf_(ref)=15·10³ Hz and N_(f,ref)        =2048.    -   Multiple OFDM numerologies are supported as given by Table 6        where and μ the cyclic prefix for a bandwidth part are obtained        from the higher-layer parameter subcarrierSpacing and        cyclicPrefix, respectively.

TABLE 6 μ Δf = 2^(μ) · 15 [kHz] Cyclic prefix 0 15 Normal 1 30 Normal 260 Normal, Extended 3 120 Normal 4 240 Normal

-   -   Uplink-downlink timing relation and transition time between        transmission and reception, and reception to transmission are        described herein. Downlink and uplink transmissions may be        organized into frames with T_(f)=(Δf_(max)N_(f)/1000)·T_(c)=10        ms duration, each including ten subframes of T_(sf)        =(Δf_(max)N_(f)/1000)·T_(c)=1 ms duration. The number of        consecutive OFDM symbols per subframe may be N_(symb)        ^(subframe,μ)=N_(symb) ^(slot)N_(slot) ^(subframe,μ). Each frame        may be divided into two equally-sized half-frames of five        subframes each with half-frame 0 including subframes 0-4 and        half-frame 1 including subframes 5-9. There may be one set of        frames in the uplink and one set of frames in the downlink on a        carrier. FIG. 3 illustrates an uplink-downlink timing relation.    -   Table 7 illustrates the transition time between transmission and        reception (^(N)TX—RX) and the transition time between reception        and transmission (^(N)RX_TX) for FR1 and FR2.

TABLE 7 Transition Time FR1 FR2 N_(TX) _(—) _(RX) 25600 13792 N_(RX)_(—) _(TX) 25600 13792

-   -   Uplink frame number i for transmission from the UE 102 may start        N_(TA)=(N_(TA)+N_(TA,offset))T_(c) before the start of the        corresponding downlink frame at the UE 102. N_(TA,offset) is        given by Table 7.    -   For subcarrier spacing configuration μ, slots may be numbered        n_(s) ^(μ)∈ {0, . . . , N_(slot) ^(subframe,μ)−1} in increasing        order within a subframe and n_(s,f) ^(μ)∈ {0, . . . N_(slot)        ^(frame,μ)−1} in increasing order within a frame. There are        N_(symb) ^(slot) consecutive OFDM symbols in a slot, where        N_(symb) ^(slot) depends on the cyclic prefix as given by Tables        8 and 9, respectively. The start of slot n_(s) ^(μ) in a        subframe is aligned in time with the start of OFDM symbol n_(s)        ^(μ)N_(symb) ^(slot) in the same subframe. Tables 8 depicts the        number of OFDM symbols per slot, slots per frame, and slots per        subframe for normal cyclic prefix. Table 9 depicts the number of        OFDM symbols per slot, slots per frame, and slots per subframe        for extended cyclic prefix.

TABLE 8 μ N_(symb) ^(slot) N_(slot) ^(frame, μ) N_(slot) ^(subframe, μ)0 14 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16

TABLE 9 μ N_(symb) ^(slot) N_(slot) ^(frame, μ) N_(slot) ^(subframe, μ)2 12 40 4OFDM symbols in a slot can be classified as “downlink”, “flexible”, or“uplink”. In a slot in a downlink frame, the UE 102 may assume thatdownlink transmissions only occur in “downlink” or “flexible” symbols.In a slot in an uplink frame, the UE 102 may only transmit in “uplink”or “flexible” symbols.

-   -   A UE 102 not capable of full-duplex communication is not        expected to transmit in the uplink earlier than N_(Rx-Tx)T_(c)        after the end of the last received downlink symbol in the same        cell where N_(Rx-Tx) is given by Table 7. A UE 102 not capable        of full-duplex communication is not expected to receive in the        downlink earlier than N_(Tx-Rx)T_(c) after the end of the last        transmitted uplink symbol in the same cell where N_(Tx-Rx) is        given by Table 7.    -   An antenna port may be defined such that the channel over which        a symbol on the antenna port is conveyed can be inferred from        the channel over which another symbol on the same antenna port        is conveyed. For DMRS associated with a PDSCH, the channel over        which a PDSCH symbol on one antenna port is conveyed can be        inferred from the channel over which a DMRS symbol on the same        antenna port is conveyed only if the two symbols are within the        same resource as the scheduled PDSCH, in the same slot, and in        the same Physical resource block group (PRG).

Two antenna ports are said to be quasi co-located if the large-scaleproperties of the channel over which a symbol on one antenna port isconveyed can be inferred from the channel over which a symbol on theother antenna port is conveyed. The large-scale properties include oneor more of delay spread, Doppler spread, Doppler shift, average gain,average delay, and spatial Rx parameters.

-   -   For each numerology and carrier, a resource grid of N_(grid,x)        ^(size,μ)N_(sc) ^(RB) subcarriers and N_(symb) ^(subframe,μ)        OFDM symbols may be defined, starting at common resource block        N_(grid) ^(start,μ) indicated by higher-layer signalling. There        may be one set of resource grids per transmission direction        (uplink or downlink) with the subscript x set to DL and UL for        downlink and uplink, respectively. When there is no risk for        confusion, the subscript x may be dropped. There may be one        resource grid for a given antenna port p, subcarrier spacing        configuration μ, and transmission direction (downlink or        uplink).

The carrier bandwidth N_(grid) ^(size,μ) for subcarrier spacingconfiguration μ may be given by the higher-layer parametercarrierBandwidth in the SCS-SpecificCarrier IE. The starting positionN_(grid) ^(start,μ) for subcarrier spacing configuration μ may be givenby the higher-layer parameter offsetToCarrier in the SCS-SpecificCarrierIE.

The frequency location of a subcarrier refers to the center frequency ofthat subcarrier. For the downlink, the higher-layer parameterDirectCurrentLocation in the SCS-SpecificCarrier IE may indicate thelocation of the transmitter DC subcarrier in the downlink for each ofthe numerologies configured in the downlink. Values in the range 0-3299represent the number of the DC subcarrier and the value 3300 indicatesthat the DC subcarrier is located outside the resource grid.

For the uplink, the higher-layer parameter DirectCurrentLocation in theUplinkTxDirectCurrentBWP IE may indicate the location of the transmitterDC subcarrier in the uplink for each of the configured bandwidth parts,including whether the DC subcarrier location is offset by 7.5 kHzrelative to the center of the indicated subcarrier or not. Values in therange 0-3299 represent the number of the DC subcarrier, the value 3300indicates that the DC subcarrier is located outside the resource grid,and the value 3301 indicates that the position of the DC subcarrier inthe uplink is undetermined.

-   -   Each element in the resource grid for antenna port p and        subcarrier spacing configurationμ is called a resource element        and is uniquely identified by (k,l)_(p,μ) where k is the index        in the frequency domain and 1 refers to the symbol position in        the time domain relative to some reference point. Resource        element (k,l)_(p,μ) corresponds to a physical resource and the        complex value a_(k,l) ^((p,μ)). When there is no risk for        confusion, or no particular antenna port or subcarrier spacing        is specified, the indices p and μ may be dropped, resulting in        a_(k,l) ^((p)) or a_(k,l).        In the downlink, the OFDM access scheme with cyclic prefix (CP)        may be employed, which may be also referred to as CP-OFDM. A        downlink radio frame may include multiple pairs of downlink        resource blocks (RBs), which is also referred to as physical        resource blocks (PRBs). The downlink RB pair is a unit for        assigning downlink radio resources, defined by a predetermined        bandwidth (RB bandwidth) and a time slot. The downlink RB pair        may include two downlink RBs that are continuous in the time        domain. Additionally or alternatively, the downlink RB may        include twelve sub-carriers in frequency domain and seven (for        normal CP) or six (for extended CP) OFDM symbols in time domain.        A region defined by one sub-carrier in frequency domain and one        OFDM symbol in time domain may be referred to as a resource        element (RE) and may be uniquely identified by the index pair        (k,l), where k and l are indices in the frequency and time        domains, respectively.

In the uplink, in addition to CP-OFDM, a Single-Carrier FrequencyDivision Multiple Access (SC-FDMA) access scheme may be employed, whichis also referred to as Discrete Fourier Transform-Spreading OFDM(DFT-S-OFDM). An uplink radio frame may include multiple pairs of uplinkresource blocks. The uplink RB pair is a unit for assigning uplink radioresources, defined by a predetermined bandwidth (RB bandwidth) and atime slot. The uplink RB pair may include two uplink RBs that arecontinuous in the time domain. The uplink RB may include twelvesub-carriers in frequency domain and seven (for normal CP) or six (forextended CP) OFDM/DFT-S-OFDM symbols in time domain. A region defined byone sub-carrier in the frequency domain and one OFDM/DFT-S-OFDM symbolin the time domain may be referred to as a resource element (RE) and maybe uniquely identified by the index pair (k,l) in a slot, where k and lare indices in the frequency and time domains respectively. CP-OFDM maybe defined as the case that transform precoding is not enabled/disabled.DFT-S-OFDM may be defined as the case that transform precoding isenabled.

-   -   Point A is also described herein. A resource block is defined as        N_(sc) ^(RB)=12 consecutive subcarriers in the frequency domain.        Point A serves as a common reference point for resource block        grids and may be obtained from the following. offsetToPointA for        a PCell downlink represents the frequency offset between point A        and the lowest subcarrier of the lowest resource block        overlapping with the SS/PBCH block used by the UE for initial        cell selection, expressed in units of resource blocks assuming        15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing        for FR2. absoluteFrequencyPointA for all other cases where        absoluteFrequencyPointA represents the frequency-location of        point A expressed as in ARFCN.    -   Common resource blocks are numbered from 0 and upwards in the        frequency domain for subcarrier spacing configuration μ. The        center of subcarrier 0 of common resource block 0 for subcarrier        spacing configuration μ may coincide with point A. The relation        between the common resource block number n_(CRB) ^(μ) in the        frequency domain and resource elements (k,l) for subcarrier        spacing configuration μ may be given by n_(CRB) ^(μ)=[k/N_(sc)        ^(RB)] where k is defined relative to point A such that k=0        corresponds to the subcarrier centered around point A.    -   Physical resource blocks may be defined within a bandwidth part        and numbered from 0 to N_(BWP,i) ^(size)31 1 where i is the        number of the bandwidth part. The relation between the physical        resource block n_(PRB) in bandwidth part i and the common        resource block n_(CRB) is given by n_(CRB)=n_(PRB)N_(BWP,i)        ^(start) where N_(BWP,i) ^(size) is the common resource block        where bandwidth part starts relative to common resource block 0.    -   Virtual resource blocks may be defined within a bandwidth part        and numbered from 0 to N_(BWP,i) ^(size)−1. In this case, i is        the number of the bandwidth part.    -   A bandwidth part is a subset of contiguous common resource        blocks for a given numerology μ_(i) in bandwidth part i on a        given carrier. The starting position N_(BWP,i) ^(start,μ) and        the number of resource blocks N_(BWP,i) ^(size,μ) in a bandwidth        part may fulfil N_(grid,x) ^(start,μ)≤N_(BWP,i)        ^(start,μ)<N_(grid,x) ^(start,μ)+N_(grid,x) ^(size,μ) and        N_(grid,x) ^(start,μ)<N_(BWP,i) ^(size,μ)+N_(BWP,i)        ^(start,μ)≤N_(grid,x) ^(start,μ)+N_(grid,x) ^(size,μ),        respectively.        A UE 102 can be configured with up to four bandwidth parts in        the downlink with a single downlink bandwidth part being active        at a given time. The UE 102 is not expected to receive PDSCH,        PDCCH, or CSI-RS (except for RRM) outside an active bandwidth        part.

A UE 102 can be configured with up to four bandwidth parts in the uplinkwith a single uplink bandwidth part being active at a given time. If aUE 102 is configured with a supplementary uplink, the UE 102 can inaddition be configured with up to four bandwidth parts in thesupplementary uplink with a single supplementary uplink bandwidth partbeing active at a given time. The UE 102 may not transmit PUSCH or PUCCHoutside an active bandwidth part. For an active cell, the UE 102l maynot transmit SRS outside an active bandwidth part. Unless otherwisenoted, the description in this disclosure applies to each of thebandwidth parts.

Configuration of BWP is also described herein. A UE 102 configured foroperation in bandwidth parts (BWPs) of a serving cell, may be configuredby higher layers for the serving cell with a set of at most fourbandwidth parts (BWPs) for receptions by the UE (DL BWP set) in a DLbandwidth by parameter BWP-Downlink and a set of at most four BWPs fortransmissions by the UE (UL BWP set) in an UL bandwidth by parameterBWP-Uplink.

If a UE 102 is not provided higher layer parameter initialDownlinkBWP,an initial active DL BWP may be defined by a location and number ofcontiguous PRBs, starting from a PRB with the lowest index and ending ata PRB with the highest index among PRBs of a control resource set forType0-PDCCH common search space, and a subcarrier spacing and a cyclicprefix for PDCCH reception in the control resource set for Type0-PDCCHcommon search space. Otherwise, the initial active DL BWP may beprovided by higher layer parameter initialDownlinkBWP. For operation onthe primary cell or on a secondary cell, a UE 102 may be provided aninitial active UL BWP by higher layer parameter initialuplinkBWP. If theUE 102 is configured with a supplementary UL carrier, the UE 102 may beprovided an initial UL BWP on the supplementary UL carrier by higherlayer parameter initialUplinkBWP in supplementaryUplink.

If a UE 102 has a dedicated BWP configuration, the UE 102 may beprovided by higher layer parameter firstActiveDownlinkBWP-Id a firstactive DL BWP for receptions and by higher layer parameterfirstActiveUplinkBWP-Id a first active UL BWP for transmissions on theprimary cell.

-   -   For each DL BWP or UL BWP in a set of DL BWPs or UL BWPs,        respectively, the UE 102 may be provided the following        parameters for the serving cell. A subcarrier spacing may be        provided by higher layer parameter subcarrierSpacing. A cyclic        prefix may be provided by higher layer parameter cyclicPrefix. A        first PRB and a number of contiguous PRBs may be provided by        higher layer parameter locationAndBandwidth that is interpreted        as RIV, setting N_(BWP) ^(size)=275, and the first PRB is a PRB        offset relative to the PRB indicated by higher layer parameters        offsetToCarrier and subcarrierSpacing. An index in the set of DL        BWPs or UL BWPs may be provided by respective higher layer        parameter bwp-Id. A set of BWP-common and a set of BWP-dedicated        parameters may be provided by higher layer parameters bwp-Common        and bwp-Dedicated.

For unpaired spectrum operation, a DL BWP from the set of configured DLBWPs with an index provided by higher layer parameter bwp-Id may belinked with an UL BWP from the set of configured UL BWPs with indexprovided by higher layer parameter bwp-Id when the DL BWP index and theUL BWP index are same. For unpaired spectrum operation, a UE 102 doesnot expect to receive a configuration where the center frequency for aDL BWP is different than the center frequency for an UL BWP when thebwp-Id of the DL BWP is same as the bwp-Id of the UL BWP.

For each DL BWP in a set of DL BWPs on the primary cell, a UE 102 may beconfigured with control resource sets for every type of common searchspace and for UE-specific search space. The UE 102 does not expect to beconfigured without a common search space on the PCell, or on the PSCell,of the MCG in the active DL BWP.

For each UL BWP in a set of UL BWPs of the PCell or of the PUCCH-SCell,the UE 102 may be provided configured resource sets for PUCCHtransmissions. A UE 102 may receive PDCCH and PDSCH in a DL BWPaccording to a configured subcarrier spacing and CP length for the DLBWP. A UE 102 may transmit PUCCH and PUSCH in an UL BWP according to aconfigured subcarrier spacing and CP length for the UL BWP.

If a bandwidth part indicator field is configured in DCI format 1_1, thebandwidth part indicator field value indicates the active DL BWP, fromthe configured DL BWP set. If a bandwidth part indicator field isconfigured in DCI format 0_1, the bandwidth part indicator field valueindicates the active UL BWP, from the configured UL BWP set.

If a bandwidth part indicator field is configured in DCI format 0_1 orDCI format 1_1 and indicates an UL BWP or a DL BWP different from theactive UL BWP or DL BWP, respectively, the UE 102 may, for eachinformation field in the received DCI format 0_1 or DCI format 1_1perform the following. If the size of the information field is smallerthan the one required for the DCI format 0_1 or DCI format 1_1interpretation for the UL BWP or DL BWP that is indicated by thebandwidth part indicator, respectively, the UE 102 may prepend zeros tothe information field until its size is the one required for theinterpretation of the information field for the UL BWP or DL BWP priorto interpreting the DCI format 0_1 or DCI format 1_1 information fields,respectively. If the size of the information field is larger than theone required for the DCI format 0_1 or DCI format 1_1 interpretation forthe UL BWP or DL BWP that is indicated by the bandwidth part indicator,respectively, the UE 102 may use a number of least significant bits ofDCI format 0_1 or DCI format 1_1 equal to the one required for the ULBWP or DL BWP indicated by a bandwidth part indicator prior tointerpreting the DCI format 0_1 or DCI format 1_1 information fields,respectively. The UE 102 may also set the active UL BWP or DL BWP to theUL BWP or DL BWP indicated by the bandwidth part indicator in the DCIformat 0_1 or DCI format 1_1, respectively.

A UE 102 does not expect to detect a DCI format 1_1 or a DCI format 0_1indicating respectively an active DL BWP or an active UL BWP change withthe corresponding time domain resource assignment field providing a slotoffset value for a PDSCH reception or PUSCH transmission that is smallerthan a value (e.g., delay) required by the UE 102 for an active DL BWPchange or UL BWP change.

If a UE 102 detects a DCI format 1_1 indicating an active DL BWP changefor a cell, the UE 102 is not required to receive or transmit in thecell during a time duration from the end of the third symbol of a slotwhere the UE 102 receives the PDCCH that includes the DCI format 1_1 ina scheduling cell until the beginning of a slot indicated by the slotoffset value of the time domain resource assignment field in the DCIformat 1_1.

If a UE 102 detects a DCI format 0_1 indicating an active UL BWP changefor a cell, the UE 102 is not required to receive or transmit in thecell during a time duration from the end of the third symbol of a slotwhere the UE 102 receives the PDCCH that includes the DCI format 0_1 inthe scheduling cell until the beginning of a slot indicated by the slotoffset value of the time domain resource assignment field in the DCIformat 0_1.

A UE 102 may expect to detect a DCI format 0_1 indicating active UL BWPchange, or a DCI format 1_1 indicating active DL BWP change, only if acorresponding PDCCH is received within the first 3 symbols of a slot.

For the primary cell, a UE 102 may be provided by higher layer parameterdefault-DownlinkBWP-Id with a default DL BWP among the configured DLBWPs. If a UE 102 is not provided a default DL BWP by higher layerparameter default-DownlinkBWP-Id, the default DL BWP is the initialactive DL BWP.

If a UE 102 is configured for a secondary cell with higher layerparameter default-DownlinkBWP-Id indicating a default DL BWP among theconfigured DL BWPs and the UE 102 is configured with higher layerparameter bwp-InactivityTimer indicating a timer value, the UEprocedures on the secondary cell may be the same as on the primary cellusing the timer value for the secondary cell and the default DL BWP forthe secondary cell.

If a UE 102 is configured by higher layer parameter bwp-InactivityTimerwith a timer value for the primary cell and the timer is running, the UE102 may increment the timer every interval of 1 millisecond forfrequency range 1 or every 0.5 milliseconds for frequency range 2 if therestarting conditions are met during the interval.

If a UE 102 is configured by higher layer parameter bwp-InactivityTimerwith a timer value for a secondary cell and the timer is running, the UE102 may increment the timer every interval of 1 millisecond forfrequency range 1 or every 0.5 milliseconds for frequency range 2 if therestarting conditions are not met during the interval.

For a cell where a UE 102 changes an active DL BWP due to a BWPinactivity timer expiration and for accommodating a delay in the activeDL BWP change or the active UL BWP change required by the UE 102, the UE102 is not required to receive or transmit in the cell during a timeduration from the beginning of a subframe for frequency range 1, or ofhalf of a subframe for frequency range 2, that is immediately after theBWP inactivity timer expires until the beginning of a slot where the UE102 can receive or transmit.

If a UE 102 is configured by higher layer parameterfirstActiveDownlinkBWP-Id with a first active DL BWP and by higher layerparameter firstActiveUplinkBWP-Id a first active UL BWP on a secondarycell or on a supplementary UL carrier, the UE 102 may use the indicatedDL BWP and the indicated UL BWP as the respective first active DL BWP onthe secondary cell and the first active UL BWP on the secondary cell orthe supplementary UL carrier.

For paired spectrum operation, a UE 102 may not expect to transmit aPUCCH with HARQ-ACK information on a PUCCH resource indicated by a DCIformat 1_0 or a DCI format 1_1 if the UE 102 changes its active UL BWPon the PCell between a time of a detection of the DCI format 1_0 or theDCI format 1_1 and a time of a corresponding PUCCH transmission withHARQ-ACK information. A UE 102 may not expect to monitor PDCCH when theUE 102 performs RRM measurements over a bandwidth that is not within theactive DL BWP for the UE 102.

Transmissions in multiple cells may be aggregated. Unless otherwisenoted, the description in this specification applies to each of theserving cells.

Some examples of V2X services are described herein. PSSCH may be usedfor transmitting sidelink shared channel (SL-SCH). SL-SCH may be the V2Xdata. As a resource for V2X communication, a resource pool may bedefined. A base station (gNB) 160 may transmit information on aconfiguration of one or more resource pools by system informationblock(s) (SIB(s)) or dedicated radio resource control (RRC) message(s).A UE 102 may select one resource pool and a resource within a resourcepool that is used for PSCCH and/or PSSCH. V2X service may be operated inuplink band(s).

A resource pool may be defined by a set of slots, subframes, or OFDMsymbols, or groups of OFDM symbols. A transmitter UE 102 (e.g., UE1) mayselect the resources within the resource pool and the transmitter UE 102may transmit a PSCCH and PSSCH associated with PSCCH. Here, whichresource is selected by the transmitter UE 102, the gNB 160 may transmitinformation on a resource pool and the resource(s) within the resourcepool. This information may be indicated via DCI, SIB, or dedicated RRCmessage. Alternately, the resource pool configuration may bepreconfigured by each UE (e.g., UE1 or UE2). One or more resource poolsfor V2X transmission and one or more resource pools for V2X receptionmay be separately indicated via SIB, dedicated RRC message, MAC CE, orDCI.

Next, the resource pool configuration is explained. For each resourcepool, the following information may be associated with all or part ofthe following information (e.g., resource pool information may includethe following information elements to associated with V2X parameters):BWP identity (BWP ID); waveform (CP-OFDM or DFT-S-OFDM); DMRS type(e.g., DMRS type 1 and DMRS type 2 may be specified in the Uu interface,and which type is used for PSCCH or PSSCH); additional DMRSconfiguration; whether PT-RS is transmitted or not. In addition, PTRSdensity configuration (e.g., a threshold of MCS to determine time domaindensity (e.g., all OFDM symbols, every other OFDM symbol, and so on),and a threshold of the number of scheduled PRBs to determine frequencydomain density (e.g., one subcarrier per RB, two subcarriers per RB, andso on)) may be associated with V2X parameters.

In addition, a configuration of a BWP may be used for parameters for V2Xservices. For instance, the parameters such as numerologies (subcarrierspacing), CP length, slot format (slot or mini-slot) may be configuredas parameters for the configured BWP, and these parameters may be usedfor a resource pool for sidelink communication. In other words,parameters for a BWP corresponding to the BWP ID associated with aresource pool may be used for sidelink communication. BWP(s) forsidelink may be called SL BWP(s) (sidelink BWP). BWP(s) for sidelink maybe configured as UL BWP(s) or DL BWP(s) to monitor PDCCH for sidelinkresource scheduling. SL BWP may be associated with a UL BWP and/or a DLBWP.

Here, each BWP for V2X may be configured as one UL BWP. When UL BWP forV2X resource pool is not configured, one or more resource pools may beconfigured in the initial UL BWP or other predefined BWP. Additionallyor alternately, the sidelink resource pool configuration may not beassociated with a BWP ID. In this case, the other rule such as thestarting PRB and the range of PRB length for the resource pool may beused. In other words, SL BWP may or may not be configured for sidelinktransmission. When SL BWP is configured, for the Uu interface, UL BWPmay be used for communication between the gNB 160 and the UE 102 and apredetermined/configured resource is used for sidelink resource pool andSL BWP is used for sidelink transmission. When SL BWP is not configured,a sidelink resource pool is defined by the PRB or subcarrier offset fromPoint A, or by the common resource block index, or based on the firstsubcarrier position of SS/PBCH block (the subcarrier with the lowestfrequency of SS/PBCH block). A resource pool configuration may include ascheduling method (e.g., dynamic scheduling of a PSSCH by using PSCCHscheduling (e.g., resource via SCI or DCI) or semi-persistent schedulingof a PSSCH by using PDCCH or PSCCH activation/deactivation).Semi-persistent scheduling may be activated or deactivated via MAC-CE.

A gNB-scheduled resource allocation scheme may be called transmissionmode 1 and a UE autonomous resource selection scheme may be calledtransmission mode 2.

A waveform and DMRS type may be configured for both PSCCH and PSSCH. Thewaveform and DMRS type may be separately configured for PSCCH and PSSCH.Additionally or alternately, the waveform of a PSCCH may always beCP-OFDM, and the configured/indicated waveform may be used for a PSSCHonly.

Additionally or alternately, DCI may indicate all or part of thefollowing information to a transmitter UE 102 (e.g., UE1) if the gNB 160can control the transmitter UE 102 (in-coverage case, for instance): BWPidentity (BWP ID); waveform (e.g., CP-OFDM or DFT-S-OFDM); DMRS type(e.g., DMRS type 1 and DMRS type 2 are specified in Uu interface, andwhich type is used for PSCCH or PSSCH); and/or the number of OFDMsymbols for DMRS.

For SCI in a PSCCH, all or part of the following information may beindicated to a receiver UE 102 (e.g., UE2): MCS; scheduled resourcewithin a resource pool (e.g., this may be a time resource pattern); DMRStype (e.g., type 1 and type 2); the number of OFDM symbols for DMRS type1 or type 2; and/or waveform.

A time domain pattern may be defined as a bitmap (b₀,b₁, . . . ,b_(L)).If b₁=1, the time unit for sidelink scheduling within a resourcepool may be used for PSSCH transmission. On the other hand, if b₁=0, thetime unit for sidelink scheduling within a resource pool may not be usedfor PSSCH transmission. Additionally or alternately, a frequency domainpattern may be defined. In this case, each bit in a bitmap of thefrequency domain pattern may be applied to each PRB or each group ofPRBs including a plurality of continuous/non-continuous PRBs.

The UE operations module 124 may provide information 148 to the one ormore receivers 120. For example, the UE operations module 124 may informthe receiver(s) 120 when to receive retransmissions.

The UE operations module 124 may provide information 138 to thedemodulator 114. For example, the UE operations module 124 may informthe demodulator 114 of a modulation pattern anticipated fortransmissions from the gNB 160.

The UE operations module 124 may provide information 136 to the decoder108. For example, the UE operations module 124 may inform the decoder108 of an anticipated encoding for transmissions from the gNB 160.

The UE operations module 124 may provide information 142 to the encoder150. The information 142 may include data to be encoded and/orinstructions for encoding. For example, the UE operations module 124 mayinstruct the encoder 150 to encode transmission data 146 and/or otherinformation 142. The other information 142 may include PDSCH HARQ-ACKinformation.

The encoder 150 may encode transmission data 146 and/or otherinformation 142 provided by the UE operations module 124. For example,encoding the data 146 and/or other information 142 may involve errordetection and/or correction coding, mapping data to space, time and/orfrequency resources for transmission, multiplexing, etc. The encoder 150may provide encoded data 152 to the modulator 154.

The UE operations module 124 may provide information 144 to themodulator 154. For example, the UE operations module 124 may inform themodulator 154 of a modulation type (e.g., constellation mapping) to beused for transmissions to the gNB 160. The modulator 154 may modulatethe encoded data 152 to provide one or more modulated signals 156 to theone or more transmitters 158.

The UE operations module 124 may provide information 140 to the one ormore transmitters 158. This information 140 may include instructions forthe one or more transmitters 158. For example, the UE operations module124 may instruct the one or more transmitters 158 when to transmit asignal to the gNB 160. For instance, the one or more transmitters 158may transmit during a UL subframe. The one or more transmitters 158 mayupconvert and transmit the modulated signal(s) 156 to one or more gNBs160.

Each of the one or more gNBs 160 may include one or more transceivers176, one or more demodulators 172, one or more decoders 166, one or moreencoders 109, one or more modulators 113, a data buffer 162 and a gNBoperations module 182. For example, one or more reception and/ortransmission paths may be implemented in a gNB 160. For convenience,only a single transceiver 176, decoder 166, demodulator 172, encoder 109and modulator 113 are illustrated in the gNB 160, though multipleparallel elements (e.g., transceivers 176, decoders 166, demodulators172, encoders 109 and modulators 113) may be implemented.

The transceiver 176 may include one or more receivers 178 and one ormore transmitters 117. The one or more receivers 178 may receive signalsfrom the UE 102 using one or more antennas 180 a-n. For example, thereceiver 178 may receive and downconvert signals to produce one or morereceived signals 174. The one or more received signals 174 may beprovided to a demodulator 172. The one or more transmitters 117 maytransmit signals to the UE 102 using one or more antennas 180 a -n. Forexample, the one or more transmitters 117 may upconvert and transmit oneor more modulated signals 115.

The demodulator 172 may demodulate the one or more received signals 174to produce one or more demodulated signals 170. The one or moredemodulated signals 170 may be provided to the decoder 166. The gNB 160may use the decoder 166 to decode signals. The decoder 166 may produceone or more decoded signals 164, 168. For example, a first eNB-decodedsignal 164 may comprise received payload data, which may be stored in adata buffer 162. A second eNB-decoded signal 168 may comprise overheaddata and/or control data. For example, the second eNB-decoded signal 168may provide data (e.g., PDSCH HARQ-ACK information) that may be used bythe gNB operations module 182 to perform one or more operations.

In general, the gNB operations module 182 may enable the gNB 160 tocommunicate with the one or more UEs 102. The gNB operations module 182may include a gNB scheduling module 194. The gNB scheduling module 194may perform operations for BWP configurations for V2X communication asdescribed herein.

The gNB operations module 182 may provide information 188 to thedemodulator 172. For example, the gNB operations module 182 may informthe demodulator 172 of a modulation pattern anticipated fortransmissions from the UE(s) 102.

The gNB operations module 182 may provide information 186 to the decoder166. For example, the gNB operations module 182 may inform the decoder166 of an anticipated encoding for transmissions from the UE(s) 102.

The gNB operations module 182 may provide information 101 to the encoder109. The information 101 may include data to be encoded and/orinstructions for encoding. For example, the gNB operations module 182may instruct the encoder 109 to encode information 101, includingtransmission data 105.

The encoder 109 may encode transmission data 105 and/or otherinformation included in the information 101 provided by the gNBoperations module 182. For example, encoding the data 105 and/or otherinformation included in the information 101 may involve error detectionand/or correction coding, mapping data to space, time and/or frequencyresources for transmission, multiplexing, etc. The encoder 109 mayprovide encoded data 111 to the modulator 113. The transmission data 105may include network data to be relayed to the UE 102.

The gNB operations module 182 may provide information 103 to themodulator 113. This information 103 may include instructions for themodulator 113. For example, the gNB operations module 182 may inform themodulator 113 of a modulation type (e.g., constellation mapping) to beused for transmissions to the UE(s) 102. The modulator 113 may modulatethe encoded data 111 to provide one or more modulated signals 115 to theone or more transmitters 117.

The gNB operations module 182 may provide information 192 to the one ormore transmitters 117. This information 192 may include instructions forthe one or more transmitters 117. For example, the gNB operations module182 may instruct the one or more transmitters 117 when to (or when notto) transmit a signal to the UE(s) 102. The one or more transmitters 117may upconvert and transmit the modulated signal(s) 115 to one or moreUEs 102.

It should be noted that a DL subframe may be transmitted from the gNB160 to one or more UEs 102 and that a UL subframe may be transmittedfrom one or more UEs 102 to the gNB 160. Furthermore, both the gNB 160and the one or more UEs 102 may transmit data in a standard specialsubframe.

It should also be noted that one or more of the elements or partsthereof included in the eNB(s) 160 and UE(s) 102 may be implemented inhardware. For example, one or more of these elements or parts thereofmay be implemented as a chip, circuitry or hardware components, etc. Itshould also be noted that one or more of the functions or methodsdescribed herein may be implemented in and/or performed using hardware.For example, one or more of the methods described herein may beimplemented in and/or realized using a chipset, an application-specificintegrated circuit (ASIC), a large-scale integrated circuit (LSI) orintegrated circuit, etc.

URLLC may coexist with other services (e.g., eMBB). Due to the latencyrequirement, URLLC may have a highest priority in some approaches. Someexamples of URLLC coexistence with other services are given herein(e.g., in one or more of the following Figure descriptions).

FIG. 2 is an example illustrating V2X services. A first UE 202 a(referred to as a transmitter UE or UE1) transmits the V2X data to asecond UE 202 b (referred to as receiver UE or UE2). A base station(gNB) 260 transmits the UE data or control signal(s) to the first UE 202a and/or the second UE 202 b. L1 is a radio link between gNB 260 and thefirst UE 202 a (L1 may be called Uu interface), and L2 is a radio linkbetween the first UE 202 a and the second UE 202 b (L2 may be called PC5interface).

FIG. 3 illustrates an uplink-downlink timing relation. Uplink framenumber i for transmission from a UE 102 may startN_(TA)=(N_(TA)+N_(TA,offset))T_(C) before the start of the correspondingdownlink frame i at the UE 102. N_(TA,offset) is given by Table 7.

FIG. 4 is a block diagram illustrating one implementation of a UE 402.The UE 402 may be implemented in accordance with a transmitter UE 102 ora receiver UE 102 as described in connection with FIG. 1.

Higher layer circuitry 423 may receive a higher layer message (e.g.,SIB, dedicated RRC) from a gNB 160 or uses a preconfigured configurationby the UE 402. Transmission circuitry 451 may generate a PSCCH and aPSSCH for transmission, HARQ-ACK bit, and/or retransmission signal(s).Reception circuitry 443 may receive a PSCCH, a PSSCH, HARQ-ACK bit,and/or retransmission signal(s). A digital-to-analog converter (D/A) 401may convert a digital signal to an analog signal, amplify the analogsignal, and transmission antenna 431 a may transmit the PSCCH and/orPSSCH. Reception antenna 431 b may receive the transmitted signals. Ananalog-to-digital converter (A/D) 403 may apply AGC (automatic gaincontroller) values, amplify the received signals, and convert an analogsignal to a digital signal. Transmission antenna 431 b may transmit thePSCCH and/or PSSCH.

FIG. 5 is a diagram illustrating one example of a resource grid for thedownlink. The resource grid illustrated in FIG. 5 may be utilized insome implementations of the systems and methods disclosed herein. Moredetail regarding the resource grid is given in connection with FIG. 1.

-   -   In FIG. 5, one downlink subframe 769 may include two downlink        slots 783. N^(DL) _(RB) is downlink bandwidth configuration of        the serving cell, expressed in multiples of N^(RB) _(sc), where        N^(RB) _(sc) is a resource block 789 size in the frequency        domain expressed as a number of subcarriers, and N^(DL) _(symb)        is the number of OFDM symbols 787 in a downlink slot 783. A        resource block 789 may include a number of resource elements        (RE) 791.    -   For a PCell, N^(DL) _(RB) is broadcast as a part of system        information. For an SCell (including an Licensed Assisted Access        (LAA) SCell), N^(DL) _(RB) is configured by a RRC message        dedicated to a UE 102. For PDSCH mapping, the available RE 791        may be the RE 791 whose index 1 fulfils 1≥1_(data,start) and/or        1_(data,end)≥1 in a subframe.        In the downlink, the OFDM access scheme with cyclic prefix (CP)        may be employed, which may be also referred to as CP-OFDM. In        the downlink, PDCCH, enhanced PDCCH (EPDCCH), PDSCH and the like        may be transmitted. A downlink radio frame may include multiple        pairs of downlink resource blocks (RBs) which is also referred        to as physical resource blocks (PRBs). The downlink RB pair is a        unit for assigning downlink radio resources, defined by a        predetermined bandwidth (RB bandwidth) and a time slot. The        downlink RB pair includes two downlink RBs that are continuous        in the time domain.

The downlink RB includes twelve sub-carriers in frequency domain. Thedownlink slot includes fourteen (for normal CP) or twelve (for extendedCP) OFDM symbols in time domain. A region defined by one sub-carrier infrequency domain and one OFDM symbol in time domain is referred to as aresource element (RE) and is uniquely identified by the index pair (k,l)in a slot, where k and l are indices in the frequency and time domains,respectively. While downlink subframes in one component carrier (CC) arediscussed herein, downlink subframes are defined for each CC anddownlink subframes are substantially in synchronization with each otheramong CCs.

FIG. 6 is a diagram illustrating one example of a resource grid for theuplink. The resource grid illustrated in FIG. 6 may be utilized in someimplementations of the systems and methods disclosed herein. More detailregarding the resource grid is given in connection with FIG. 1.

-   -   FIG. 6, one uplink subframe 869 may include two uplink slots        883. N^(UL) _(RB) is uplink bandwidth configuration of the        serving cell, expressed in multiples of N^(RB) _(sc), where        N^(RB) _(sc) is a resource block 889 size in the frequency        domain expressed as a number of subcarriers, and N^(UL) _(symb)        is the number of SC-FDMA symbols 893 in an uplink slot 883. A        resource block 889 may include a number of resource elements        (RE) 891.    -   For a PCell, N^(UL) _(RB) is broadcast as a part of system        information. For an SCell (including an LAA Scell), N^(UL) _(RB)        is configured by a RRC message dedicated to a UE 102.

In the uplink, in addition to CP-OFDM, a Single-Carrier FrequencyDivision Multiple Access (SC-FDMA) access scheme may be employed, whichis also referred to as Discrete Fourier Transform-Spreading OFDM(DFT-S-OFDM). In the uplink, PUCCH, PUSCH, PRACH and the like may betransmitted. An uplink radio frame may include multiple pairs of uplinkresource blocks. The uplink RB pair is a unit for assigning uplink radioresources, defined by a predetermined bandwidth (RB bandwidth) and atime slot. The uplink RB pair includes two uplink RBs that arecontinuous in the time domain.

The uplink RB may include twelve sub-carriers in frequency domain. Theuplink slot includes fourteen (for normal CP) or twelve (for extendedCP) OFDM/DFT-S-OFDM symbols in time domain. A region defined by onesub-carrier in the frequency domain and one OFDM/DFT-S-OFDM symbol inthe time domain is referred to as a RE and is uniquely identified by theindex pair (k,l) in a slot, where k and l are indices in the frequencyand time domains respectively. While uplink subframes in one componentcarrier (CC) are discussed herein, uplink subframes are defined for eachCC.

FIG. 7 shows examples of several numerologies 901. The numerology #1 901a may be a basic numerology (e.g., a reference numerology). For example,a RE 995 a of the basic numerology 901 a may be defined with subcarrierspacing 905 a of 15 kHz in frequency domain and 2048Ts+CP length (e.g.,160Ts or 144Ts) in time domain (i.e., symbol length #1 903 a), where Tsdenotes a baseband sampling time unit defined as 1/(15000*2048) seconds.For the i-th numerology, the subcarrier spacing 905 may be equal to15*2^(i) and the effective OFDM symbol length 2048*2^(−i)*Ts. It maycause the symbol length is 2048*2^(−i) *Ts+CP length (e.g., 160*2^(−i)*Ts or 144*2^(−i) *Ts). In other words, the subcarrier spacing of thei+1-th numerology is a double of the one for the i-th numerology, andthe symbol length of the i+1-th numerology is a half of the one for thei-th numerology. FIG. 7 shows four numerologies, but the system maysupport another number of numerologies. Furthermore, the system does nothave to support all of the 0-th to the I-th numerologies, i=0, 1, . . ., I.

For example, the first UL transmission on the first SPS resource asabove mentioned may be performed only on the numerology #1 (e.g., asubcarrier spacing of 15 kHz). Here, the UE 102 may acquire (detect) thenumerology #1 based on a synchronization signal. Also, the UE 102 mayreceive a dedicated RRC signal including information (e.g., a handovercommand) configuring the numerology #1. The dedicated RRC signal may bea UE-specific signal. Here, the first UL transmission on the first SPSresource may be performed on the numerology #1, the numerology #2 (asubcarrier spacing of 30 kHz), and/or the numerology #3 (a subcarrierspacing of 60 kHz).

Also, the second UL transmission on the second SPS resource as abovementioned may be performed only on the numerology #3. Here, for example,the UE 102 may receive System Information (e.g., Master InformationBlock (MIB) and/or System Information Block (SIB)) including informationconfiguring the numerology #2 and/or the numerology #3.

Also, the UE 102 may receive the dedicated RRC signal includinginformation (e.g., the handover command) configuring the numerology #2and/or the numerology #3. The System Information (e.g., MIB) may betransmitted on BCH (Broadcast Channel) and/or the dedicated RRC signal.The System Information (e.g., SIB) may contain information relevant whenevaluating if a UE 102 is allowed to access a cell and/or defines thescheduling of other system information. The System Information (SIB) maycontain radio resource configuration information that is common formultiple UEs 102. Namely, the dedicated RRC signal may include each ofmultiple numerology configurations (the first numerology, the secondnumerology, and/or the third numerology) for each of UL transmissions(e.g., each of UL-SCH transmissions, each of PUSCH transmissions). Also,the dedicated RRC signal may include each of multiple numerologyconfigurations (the first numerology, the second numerology, and/or thethird numerology) for each of DL transmissions (each of PDCCHtransmissions).

-   -   FIG. 8 shows examples of subframe structures for the        numerologies 1001 that are shown in FIG. 7. Given that a slot        1083 includes N^(DL) _(symb) (or N^(UL) _(symb))=7 symbols, the        slot length of the i+1-th numerology 1001 is a half of the one        for the i-th numerology 1001, and eventually the number of slots        1083 in a subframe (i.e., 1 ms) becomes double. It may be noted        that a radio frame may include 10 subframes, and the radio frame        length may be equal to 10 ms.    -   FIG. 9 shows examples of slots 1183 and sub-slots 1107. If a        sub-slot 1107 is not configured by higher layer, the UE 102 and        the eNB/gNB 160 may only use a slot 1183 as a scheduling unit.        More specifically, a given transport block may be allocated to a        slot 1183. If the sub-slot 1107 is configured by higher layer,        the UE 102 and the eNB/gNB 160 may use the sub-slot 1107 as well        as the slot 1183. The sub-slot 1107 may include one or more OFDM        symbols. The maximum number of OFDM symbols that constitute the        sub-slot 1107 may be N^(DL) _(symb)-1 (or N^(UL) _(symb)-1).

The sub-slot length may be configured by higher layer signaling.Alternatively, the sub-slot length may be indicated by a physical layercontrol channel (e.g., by DCI format).

-   -   The sub-slot 1107 may start at any symbol within a slot 1183        unless it collides with a control channel. There could be        restrictions of mini-slot length based on restrictions on        starting position. For example, the sub-slot 1107 with the        length of N^(DL) _(symb)-1 (or N^(NL) _(symb)-1) may start at        the second symbol in a slot 1183. The starting position of a        sub-slot 1107 may be indicated by a physical layer control        channel (e.g., by DCI format). Alternatively, the starting        position of a sub-slot 1107 may be derived from information        (e.g., search space index, blind decoding candidate index,        frequency and/or time resource indices, PRS index, a control        channel element index, control channel element aggregation        level, an antenna port index, etc.) of the physical layer        control channel which schedules the data in the concerned        sub-slot 1107. Here, a slot may be called “PDSCH type A”, “PUSCH        type A”, or “PSSCH type A”. A mini-slot may be called “PDSCH        type B”, “PUSCH type B”, or “PSSCH type B”. This may be defined        as the position of DMRS in the time domain. For example, DMRS of        PSSCH type A may be mapped to the 3rd or 4th OFDM symbol in a        slot, and DMRS of PSSCH type B may be mapped to the first OFDM        symbol of the scheduled OFDM symbol(s).        In cases when the sub-slot 1107 is configured, a given transport        block may be allocated to either a slot 1183, a sub-slot 1107,        aggregated sub-slots 1107 or aggregated subslot(s) 1107 and slot        1183. This unit may also be a unit for HARQ-ACK bit generation.

FIG. 10 shows examples of scheduling timelines 1209. For a normal DLscheduling timeline 1209 a, DL control channels are mapped the initialpart of a slot 1283 a. The DL control channels 1211 schedule DL sharedchannels 1213 a in the same slot 1283 a. HARQ-ACKs for the DL sharedchannels 1213 a (i.e., HARQ-ACKs each of which indicates whether or nottransport block in each DL shared channel 1213 a is detectedsuccessfully) are reported via UL control channels 1215 a in a laterslot 1283 b. In this instance, a given slot 1283 may contain either oneof DL transmission and UL transmission.

For a normal UL scheduling timeline 1209 b, DL control channels 1211 bare mapped the initial part of a slot 1283 c. The DL control channels1211 b schedule UL shared channels 1217 a in a later slot 1283 d. Forthese cases, the association timing (time shift) between the DL slot1283 c and the UL slot 1283 d may be fixed or configured by higher layersignaling. Alternatively, it may be indicated by a physical layercontrol channel (e.g., the DL assignment DCI format, the UL grant DCIformat, or another DCI format such as UE-common signaling DCI formatwhich may be monitored in common search space).

For a self-contained base DL scheduling timeline 1209 c, DL controlchannels 1211 c are mapped to the initial part of a slot 1283 e. The DLcontrol channels 1211 c schedule DL shared channels 1213 b in the sameslot 1283 e. HARQ-ACKs for the DL shared channels 1213 b are reported inUL control channels 1215 b, which are mapped at the ending part of theslot 1283 e.

For a self-contained base UL scheduling timeline 1209 d, DL controlchannels 1211 d are mapped to the initial part of a slot 1283 f. The DLcontrol channels 1211 d schedule UL shared channels 1217 b in the sameslot 1283 f. For these cases, the slot 1283 f may contain DL and ULportions, and there may be a guard period between the DL and ULtransmissions.

The use of a self-contained slot may be upon a configuration ofself-contained slot. Alternatively, the use of a self-contained slot maybe upon a configuration of the sub-slot. Yet alternatively, the use of aself-contained slot may be upon a configuration of shortened physicalchannel (e.g., PDSCH, PUSCH, PUCCH, etc.).

FIG. 11 shows examples of DL control channel monitoring regions. One ormore sets of PRB(s) may be configured for DL control channel monitoring.In other words, a control resource set is, in the frequency domain, aset of PRBs within which the UE 102 attempts to blindly decode downlinkcontrol information, where the PRBs may or may not be frequencycontiguous, a UE 102 may have one or more control resource sets, and oneDCI message may be located within one control resource set. In thefrequency-domain, a PRB is the resource unit size (which may or may notinclude Demodulation reference signals (DM-RS)) for a control channel. ADL shared channel may start at a later OFDM symbol than the one(s) whichcarries the detected DL control channel. Alternatively, the DL sharedchannel may start at (or earlier than) an OFDM symbol than the last OFDMsymbol which carries the detected DL control channel. In other words,dynamic reuse of at least part of resources in the control resource setsfor data for the same or a different UE 102, at least in the frequencydomain may be supported.

FIG. 12 shows examples of DL control channel which includes more thanone control channel elements. When the control resource set spansmultiple OFDM symbols, a control channel candidate may be mapped tomultiple OFDM symbols or may be mapped to a single OFDM symbol. One DLcontrol channel element may be mapped on REs defined by a single PRB anda single OFDM symbol. If more than one DL control channel elements areused for a single DL control channel transmission, DL control channelelement aggregation may be performed.

The number of aggregated DL control channel elements is referred to asDL control channel element aggregation level. The DL control channelelement aggregation level may be 1 or 2 to the power of an integer. ThegNB 160 may inform a UE 102 of which control channel candidates aremapped to each subset of OFDM symbols in the control resource set. Ifone DL control channel is mapped to a single OFDM symbol and does notspan multiple OFDM symbols, the DL control channel element aggregationis performed within an OFDM symbol, namely multiple DL control channelelements within an OFDM symbol are aggregated. Otherwise, DL controlchannel elements in different OFDM symbols can be aggregated.

FIG. 13 shows examples of UL control channel structures. UL controlchannel may be mapped on REs which are defined a PRB and a slot infrequency and time domains, respectively. This UL control channel may bereferred to as a long format (or just the 1st format). UL controlchannels may be mapped on REs on a limited OFDM symbols in time domain.This may be referred to as a short format (or just the 2nd format). TheUL control channels with a short format may be mapped on REs within asingle PRB. Alternatively, the UL control channels with a short formatmay be mapped on REs within multiple PRB s. For example, interlacedmapping may be applied, namely the UL control channel may be mapped toevery N PRBs (e.g. 5 or 10) within a system bandwidth.

FIG. 14 is a block diagram illustrating one implementation of a gNB1660. The gNB 1660 may include a higher layer processor 1623, a DLtransmitter 1625, a UL receiver 1633, and one or more antenna 1631. TheDL transmitter 1625 may include a PDCCH transmitter 1627 and a PDSCHtransmitter 1629. The UL receiver 1633 may include a PUCCH receiver 1635and a PUSCH receiver 1637.

The higher layer processor 1623 may manage physical layer's behaviors(the DL transmitter's and the UL receiver's behaviors) and providehigher layer parameters to the physical layer. The higher layerprocessor 1623 may obtain transport blocks from the physical layer. Thehigher layer processor 1623 may send/acquire higher layer messages suchas an RRC message and MAC message to/from a UE's higher layer. Thehigher layer processor 1623 may provide the PDSCH transmitter transportblocks and provide the PDCCH transmitter transmission parameters relatedto the transport blocks.

The DL transmitter 1625 may multiplex downlink physical channels anddownlink physical signals (including reservation signal) and transmitthem via transmission antennas 1631. The UL receiver 1633 may receivemultiplexed uplink physical channels and uplink physical signals viareceiving antennas 1631 and de-multiplex them. The PUCCH receiver 1635may provide the higher layer processor 1623 UCI. The PUSCH receiver 1637may provide the higher layer processor 1623 received transport blocks.

FIG. 15 is a block diagram illustrating one implementation of a UE 1702.The UE 1702 may include a higher layer processor 1723, a UL transmitter1751, a DL receiver 1743, and one or more antenna 1731. The ULtransmitter 1751 may include a PUCCH transmitter 1753 and a PUSCHtransmitter 1755. The DL receiver 1743 may include a PDCCH receiver 1745and a PDSCH receiver 1747.

The higher layer processor 1723 may manage physical layer's behaviors(the UL transmitter's and the DL receiver's behaviors) and providehigher layer parameters to the physical layer. The higher layerprocessor 1723 may obtain transport blocks from the physical layer. Thehigher layer processor 1723 may send/acquire higher layer messages suchas an RRC message and MAC message to/from a UE's higher layer. Thehigher layer processor 1723 may provide the PUSCH transmitter transportblocks and provide the PUCCH transmitter 1753 UCI.

The DL receiver 1743 may receive multiplexed downlink physical channelsand downlink physical signals via receiving antennas 1731 andde-multiplex them. The PDCCH receiver 1745 may provide the higher layerprocessor 1723 DCI. The PDSCH receiver 1747 may provide the higher layerprocessor 1723 received transport blocks.

It should be noted that names of physical channels described herein areexamples. The other names such as “NRPDCCH, NRPDSCH, NRPUCCH andNRPUSCH”, “new Generation-(G)PDCCH, GPDSCH, GPUCCH and GPUSCH” or thelike can be used.

FIG. 16 illustrates various components that may be utilized in a UE1802. The UE 1802 described in connection with FIG. 16 may beimplemented in accordance with the UE 102 described in connection withFIG. 1. The UE 1802 includes a processor 1803 that controls operation ofthe UE 1802. The processor 1803 may also be referred to as a centralprocessing unit (CPU). Memory 1805, which may include read-only memory(ROM), random access memory (RAM), a combination of the two or any typeof device that may store information, provides instructions 1807 a anddata 1809 a to the processor 1803. A portion of the memory 1805 may alsoinclude non-volatile random-access memory (NVRAM). Instructions 1807 band data 1809 b may also reside in the processor 1803. Instructions 1807b and/or data 1809 b loaded into the processor 1803 may also includeinstructions 1807 a and/or data 1809 a from memory 1805 that were loadedfor execution or processing by the processor 1803. The instructions 1807b may be executed by the processor 1803 to implement the methodsdescribed above.

The UE 1802 may also include a housing that contains one or moretransmitters 1858 and one or more receivers 1820 to allow transmissionand reception of data. The transmitter(s) 1858 and receiver(s) 1820 maybe combined into one or more transceivers 1818. One or more antennas1822 a-n are attached to the housing and electrically coupled to thetransceiver 1818.

The various components of the UE 1802 are coupled together by a bussystem 1811, which may include a power bus, a control signal bus and astatus signal bus, in addition to a data bus. However, for the sake ofclarity, the various buses are illustrated in FIG. 16 as the bus system1811. The UE 1802 may also include a digital signal processor (DSP) 1813for use in processing signals. The UE 1802 may also include acommunications interface 1815 that provides user access to the functionsof the UE 1802. The UE 1802 illustrated in FIG. 16 is a functional blockdiagram rather than a listing of specific components.

FIG. 17 illustrates various components that may be utilized in a gNB1960. The gNB 1960 described in connection with FIG. 17 may beimplemented in accordance with the gNB 160 described in connection withFIG. 1. The gNB 1960 includes a processor 1903 that controls operationof the gNB 1960. The processor 1903 may also be referred to as a centralprocessing unit (CPU). Memory 1905, which may include read-only memory(ROM), random access memory (RAM), a combination of the two or any typeof device that may store information, provides instructions 190 a anddata 1909 a to the processor 1903. A portion of the memory 1905 may alsoinclude non-volatile random-access memory (NVRAM). Instructions 1907 band data 1909 b may also reside in the processor 1903. Instructions 1907b and/or data 1909 b loaded into the processor 1903 may also includeinstructions 1907 a and/or data 1909 a from memory 1905 that were loadedfor execution or processing by the processor 1903. The instructions 1907b may be executed by the processor 1903 to implement the methodsdescribed above.

The gNB 1960 may also include a housing that contains one or moretransmitters 1917 and one or more receivers 1978 to allow transmissionand reception of data. The transmitter(s) 1917 and receiver(s) 1978 maybe combined into one or more transceivers 1976. One or more antennas1980 a-n are attached to the housing and electrically coupled to thetransceiver 1976.

The various components of the gNB 1960 are coupled together by a bussystem 1911, which may include a power bus, a control signal bus and astatus signal bus, in addition to a data bus. However, for the sake ofclarity, the various buses are illustrated in FIG. 17 as the bus system1911. The gNB 1960 may also include a digital signal processor (DSP)1913 for use in processing signals. The gNB 1960 may also include acommunications interface 1915 that provides user access to the functionsof the gNB 1960. The gNB 1960 illustrated in FIG. 17 is a functionalblock diagram rather than a listing of specific components.

FIG. 18 is a block diagram illustrating one implementation of a UE 2002in which BWP configurations for V2X communication may be implemented.The UE 2002 includes transmit means 2058, receive means 2020 and controlmeans 2024. The transmit means 2058, receive means 2020 and controlmeans 2024 may be configured to perform one or more of the functionsdescribed in connection with FIG. 1 above. FIG. 16 above illustrates oneexample of a concrete apparatus structure of FIG. 18. Other variousstructures may be implemented to realize one or more of the functions ofFIG. 1. For example, a DSP may be realized by software.

FIG. 19 is a block diagram illustrating one implementation of a gNB 2160in which BWP configurations for V2X communication may be implemented.The gNB 2160 includes transmit means 2123, receive means 2178 andcontrol means 2182. The transmit means 2123, receive means 2178 andcontrol means 2182 may be configured to perform one or more of thefunctions described in connection with FIG. 1 above. FIG. 17 aboveillustrates one example of a concrete apparatus structure of FIG. 19.Other various structures may be implemented to realize one or more ofthe functions of FIG. 1. For example, a DSP may be realized by software.

-   -   The term “computer-readable medium” refers to any available        medium that can be accessed by a computer or a processor. The        term “computer-readable medium,” as used herein, may denote a        computer- and/or processor-readable medium that is        non-transitory and tangible. By way of example, and not        limitation, a computer-readable or processor-readable medium may        comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage,        magnetic disk storage or other magnetic storage devices, or any        other medium that can be used to carry or store desired program        code in the form of instructions or data structures and that can        be accessed by a computer or processor. Disk and disc, as used        herein, includes compact disc (CD), laser disc, optical disc,        digital versatile disc (DVD), floppy disk and Blu-ray® disc        where disks usually reproduce data magnetically, while discs        reproduce data optically with lasers.        It should be noted that one or more of the methods described        herein may be implemented in and/or performed using hardware.        For example, one or more of the methods described herein may be        implemented in and/or realized using a chipset, an        application-specific integrated circuit (ASIC), a large-scale        integrated circuit (LSI) or integrated circuit, etc.

Each of the methods disclosed herein comprises one or more steps oractions for achieving the described method. The method steps and/oractions may be interchanged with one another and/or combined into asingle step without departing from the scope of the claims. In otherwords, unless a specific order of steps or actions is required forproper operation of the method that is being described, the order and/oruse of specific steps and/or actions may be modified without departingfrom the scope of the claims.

It is to be understood that the claims are not limited to the preciseconfiguration and components illustrated above. Various modifications,changes and variations may be made in the arrangement, operation anddetails of the systems, methods, and apparatus described herein withoutdeparting from the scope of the claims.

A program running on the gNB 160 or the UE 102 according to thedescribed systems and methods is a program (a program for causing acomputer to operate) that controls a CPU and the like in such a manneras to realize the function according to the described systems andmethods. Then, the information that is handled in these apparatuses istemporarily stored in a RAM while being processed. Thereafter, theinformation is stored in various ROMs or HDDs, and whenever necessary,is read by the CPU to be modified or written. As a recording medium onwhich the program is stored, among a semiconductor (for example, a ROM,a nonvolatile memory card, and the like), an optical storage medium (forexample, a DVD, a MO, a MD, a CD, a BD, and the like), a magneticstorage medium (for example, a magnetic tape, a flexible disk, and thelike), and the like, any one may be possible. Furthermore, in somecases, the function according to the described systems and methodsdescribed above is realized by running the loaded program, and inaddition, the function according to the described systems and methods isrealized in conjunction with an operating system or other applicationprograms, based on an instruction from the program.

Furthermore, in a case where the programs are available on the market,the program stored on a portable recording medium can be distributed orthe program can be transmitted to a server computer that connectsthrough a network such as the Internet. In this case, a storage devicein the server computer also is included. Furthermore, some or all of thegNB 160 and the UE 102 according to the systems and methods describedabove may be realized as an LSI that is a typical integrated circuit.Each functional block of the gNB 160 and the UE 102 may be individuallybuilt into a chip, and some or all functional blocks may be integratedinto a chip. Furthermore, a technique of the integrated circuit is notlimited to the LSI, and an integrated circuit for the functional blockmay be realized with a dedicated circuit or a general-purpose processor.Furthermore, if with advances in a semiconductor technology, atechnology of an integrated circuit that substitutes for the LSIappears, it is also possible to use an integrated circuit to which thetechnology applies.

Moreover, each functional block or various features of the base stationdevice and the terminal device used in each of the aforementionedimplementations may be implemented or executed by a circuitry, which istypically an integrated circuit or a plurality of integrated circuits.The circuitry designed to execute the functions described in the presentspecification may comprise a general-purpose processor, a digital signalprocessor (DSP), an application specific or general applicationintegrated circuit (ASIC), a field programmable gate array (FPGA), orother programmable logic devices, discrete gates or transistor logic, ora discrete hardware component, or a combination thereof. Thegeneral-purpose processor may be a microprocessor, or alternatively, theprocessor may be a conventional processor, a controller, amicrocontroller or a state machine. The general-purpose processor oreach circuit described above may be configured by a digital circuit ormay be configured by an analogue circuit. Further, when a technology ofmaking into an integrated circuit superseding integrated circuits at thepresent time appears due to advancement of a semiconductor technology,the integrated circuit by this technology is also able to be used.

As used herein, the term “and/or” should be interpreted to mean one ormore items. For example, the phrase “A, B and/or C” should beinterpreted to mean any of: only A, only B, only C, A and B (but not C),B and C (but not A), A and C (but not B), or all of A, B, and C. As usedherein, the phrase “at least one of” should be interpreted to mean oneor more items. For example, the phrase “at least one of A, B and C” orthe phrase “at least one of A, B or C” should be interpreted to mean anyof: only A, only B, only C, A and B (but not C), B and C (but not A), Aand C (but not B), or all of A, B, and C. As used herein, the phrase“one or more of” should be interpreted to mean one or more items. Forexample, the phrase “one or more of A, B and C” or the phrase “one ormore of A, B or C” should be interpreted to mean any of: only A, only B,only C, A and B (but not C), B and C (but not A), A and C (but not B),or all of A, B, and C.

<Summary>

In one example, a user equipment (UE), comprising: higher layercircuitry configured to receive information on a resource pool forsidelink; transmitting circuitry configured to transmit a physicalsidelink control channel (PSCCH) and a physical sidelink shared channel(PSSCH), wherein the information on the resource pool includesinformation on a bandwidth part identity (BWP ID); and the transmittingcircuitry is configured to transmit the PSSCH on a BWP associated withthe BWP ID.

In one example, a base station (gNB), comprising: transmitting circuitryconfigured to transmit information on a resource pool for sidelink; andreceiving circuitry configured to receive a physical sidelink controlchannel (PSCCH) and a physical sidelink shared channel (PSSCH), whereinthe information on the resource pool includes information on a bandwidthpart identity (BWP ID); and the receiving circuitry is configured toreceive the PSSCH on a BWP associated with the BWP ID.

In one example, a communication method by a user equipment (UE),comprising: receiving information on a resource pool for sidelink;transmitting a physical sidelink control channel (PSCCH) and a physicalsidelink shared channel (PSSCH), wherein the information on the resourcepool includes information on a bandwidth part identity (BWP ID); andtransmitting the PSSCH on a BWP associated with the BWP ID.

In one example, a communication method by a base station (gNB),comprising: transmitting information on a resource pool for sidelink;receiving a physical sidelink control channel (PSCCH) and a physicalsidelink shared channel (PSSCH), wherein the information on the resourcepool includes information on a bandwidth part identity (BWP ID); andreceiving the PSSCH on a BWP associated with the BWP ID.

In one example, a user equipment (UE), comprising: higher layercircuitry configured to receive first information to configure asidelink bandwidth part (BWP) and second information to configure one ormore resource pool for sidelink transmission and/or reception;transmitting circuitry configured to transmit a physical sidelinkcontrol channel (PSCCH) and a physical sidelink shared channel (PSSCH),wherein the first information includes a configuration of numerologiesfor the PSCCH and PSSCH; and the second information includes aconfiguration of one or more resource pools for the PSCCH and PSSCHwithin the sidelink BWP.

In one example, a base station (gNB), comprising: higher layer circuitryconfigured to transmit first information to configure a sidelinkbandwidth part (BWP) and second information to configure one or moreresource pool for sidelink communication; wherein the first informationincludes a configuration of numerologies for the PSCCH and PSSCH; andthe second information includes a configuration of one or more resourcepools for the PSCCH and PSSCH within the sidelink BWP.

In one example, a communication method by a user equipment (UE),comprising: receiving first information to configure a sidelinkbandwidth part (BWP) and second information to configure one or moreresource pool for sidelink transmission and/or reception; transmitting aphysical sidelink control channel (PSCCH) and a physical sidelink sharedchannel (PSSCH), wherein the first information includes a configurationof numerologies for the PSCCH and PSSCH; and the second informationincludes a configuration of one or more resource pools for the PSCCH andPSSCH within the sidelink BWP.

In one example, a communication method by a base station (gNB),comprising: transmitting first information to configure a sidelinkbandwidth part (BWP) and second information to configure one or moreresource pool for sidelink communication; wherein the first informationincludes a configuration of numerologies for the PSCCH and PSSCH; andthe second information includes a configuration of one or more resourcepools for the PSCCH and PSSCH within the sidelink BWP.

<Cross Reference>

This Nonprovisional application claims priority under 35 U.S.C. § 119 onprovisional Application No. 62/737,737 on Sep. 27, 2018, the entirecontents of which are hereby incorporated by reference.

What is claimed is:
 1. A user equipment (UE), comprising: higher layercircuitry configured to receive first information to configure asidelink bandwidth part (BWP) and second information to configure one ormore resource pool for sidelink transmission and/or reception;transmitting circuitry configured to transmit a physical sidelinkcontrol channel (PSCCH) and a physical sidelink shared channel (PSSCH),wherein the first information includes a configuration of numerologiesfor the PSCCH and PSSCH; and the second information includes aconfiguration of one or more resource pools for the PSCCH and PSSCHwithin the sidelink BWP.
 2. A base station (gNB), comprising: higherlayer circuitry configured to transmit first information to configure asidelink bandwidth part (BWP) and second information to configure one ormore resource pool for sidelink communication; wherein the firstinformation includes a configuration of numerologies for the PSCCH andPSSCH; and the second information includes a configuration of one ormore resource pools for the PSCCH and PSSCH within the sidelink BWP. 3.A communication method by a user equipment (UE), comprising: receivingfirst information to configure a sidelink bandwidth part (BWP) andsecond information to configure one or more resource pool for sidelinktransmission and/or reception; transmitting a physical sidelink controlchannel (PSCCH) and a physical sidelink shared channel (PSSCH), whereinthe first information includes a configuration of numerologies for thePSCCH and PSSCH; and the second information includes a configuration ofone or more resource pools for the PSCCH and PSSCH within the sidelinkBWP.
 4. A communication method by a base station (gNB), comprising:transmitting first information to configure a sidelink bandwidth part(BWP) and second information to configure one or more resource pool forsidelink communication; wherein the first information includes aconfiguration of numerologies for the PSCCH and PSSCH; and the secondinformation includes a configuration of one or more resource pools forthe PSCCH and PSSCH within the sidelink BWP.